• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    METHOD FOR SETTING UP A USER EQUIPMENT, METHOD SET TO BE TRANSFERRED FROM A SOURCE BASE STATION TO A TARGET BASE STATION IN A TRANSFER SCENARIO, BASE STATION, AND, USER EQUIPMENT. Methods and arrangements on a base station and User Equipment are provided. Arrangement methods concern the scenario when the UE is transferred from a source base station to a target base station in a handover scenario, and in which the target base station may not support features in which the source base station and UE support . The method at the UE comprises receiving (501) a setup message from a target base station via the source base station, configuring (502) the UE based on the setup message received from the target base station searching (503) for a second field in an information element of the received configuration message. The presence/non-presence or a value of the second field is indicative of how to manage a first configured functionality associated with an optional first field, where the first configured functionality may not be supported by the target base station.
    公开号:BR112012007188B1
    申请号:R112012007188-2
    申请日:2010-06-03
    公开日:2021-06-08
    发明作者:Janne Peisa；Tao Cui；Ingrid Nordstrand；Mats Sagfors；Sven Ekemark
    申请人:Telefonaktiebolaget Lm Ericsson (Publ)；
    IPC主号:
    专利说明:

    Technical Field
    [001] The present invention relates to methods and arrangements in a telecommunication system, in particular to methods and arrangements for use in working networks comprising base stations, in which base stations may have different radio resource control capabilities. Fundamentals
    [002] Radio Resource Control (RCC) protocol in Long Term Evolution (LTE) 3GPP, also referred to as Evolved UTRAN (E-UTRAN), is the indicating protocol to configure and reconfigure the radio interface configuration of User Equipment (Ues), also called mobile terminals. The protocol is disclosed in technical specification document 3GPP TS 36.331.
    [003] The first version, Rel-8, of the RRX (described in 3GPP TS 36.331) of LTE implements a solution where fields in Information Elements (IEs) can be omitted from a message. An IE consists of fields. Each field comprises individual content or IE which in turn comprises composing or IE. In addition a message comprises a plurality of Ies as illustrated in figure 1. In the 3GPP TS 36.331 technical specification document the IE and field are defined as follows:
    [004] Information Element: A structural element containing a single or multiple fields is referred to as an information element.
    [005] Field: The individual contents of an information element are referred to as fields.
    [006] The use of fields in IEs can be optional. If a field in an IE is optional, the behavior of the UE is typically specified for the case where such a field is absent. One motivation for defining optional fields in messages is to reduce or minimize the size of referral messages. A typical situation is the case where only parts of the User Equipment (UE) configuration are changed with a message where most of the UE configuration remains unchanged. Thus, it is often specified that a terminal must continue with a specific function when the related field, which is optional in the message in question, is not present in the received message.
    [007] An example of the optional field is illustrated below where an IE comprising a plurality of fields is disclosed. The Channel Quality (CQI) indication is configured with an Information Element called CQI-ReportConfig:

    [008] Within this IE, both cqLReportModeAperiodic and cqi-ReportPeriodic are optional fields, which is indicated with the OPTIONAL syntax above.
    [009] Thus the behavior of UR has to be specified when optional parameters are absent. This can be done using the indication “Need OR” and “Need ON”, respectively, which specify the behavior of the UE when optional parameters are not present. Need OR means that in case the information element is absent from a message, then the UE must stop using/discontinue or delete any existing setting or values that will otherwise be set if the information element is present. In contrast, with the Need ON indication, the absence of the information element means that the UE must continue to use the existing values and associated functionality. In the following, the behavior where the UE must keep the configuration and related functionality without changing any parameters in time when an optional field is lost, is called “Optional continue”.
    [0010] Also other conditions and functional behavior can be explicitly specified in the specification procedures, eg different behaviors can be specified when an optional field is missing from a relevant message. For example, also IE CQI-ReportConfig is OPTIONAL in IE PhysicalConfigDedicated. IE PhysicalConfigDedicated is in turn “Optional Continue” in IE RadioResourceConfigDedicated, which in turn is optional in the RRCConnectionReconfiguration message. RRCConnectionReconfiguration is the message sent from UETRAN to a UE to configure and reconfigure functionality and related parameters in a UE. Thus, the solution to “Optional continue” is used in the specification so that only those fields of relevance to the desired reconfiguration need to be included in the message IE.
    [0011] The above mentioned solution using “optional continue” is used, eg in intra-LTE mobility. This is also illustrated in figure 2. Next, in case a mobile terminal transfer occurs from a first cell to a second cell, the first cell is denoted the Source Cell and the second cell is denoted the Target Cell. Similarly, where cells are controlled by different base stations, this is denoted Source eNB and Target eNB, respectively. eNBs are also referred to as base stations in this specification. The desire is to exchange only small messages between the UE and eNBs in the transfer. It can be assumed that many of the features used in the Source Cell will remain unmodified in the Target Cell, and it will then not be necessary to reconfigure all the features in the Target Cell.
    Thus if the transfer takes place between different eNBs, eg from a Source eNB to a Target eNB, the source eNB sends total UE configuration to the Target eNB in preparation for the transfer. The TRANSFER REQUEST message from the source eNB contains the RCC Context which includes the RRC HandoverPreparationlnformation message as defined in 3GPP TS 36.331. The Target eNB can now, after decoding the received Access Layer Context, decide which parts of the UE configuration are acceptable without change, and which parts should be reconfigured. For example, nearby base stations operated by the same operator and possibly manufactured by a single vendor are likely to prefer the same parameters as describing periodic CQI reports. In such a case, there is no need for the Target eNB to send any update configuration to the UE, as the Target readily accepts this part of the current UE configuration. However, if it happens that the Target eNB implements eg a different Random Access configuration compared to Source eNB, it may happen that Target needs to update some Random Access parameters of relevance in the UE.
    [0013] Subsequently, the Target eNB sends in the TRANSFER REQUEST KNOWLEDGE a "Transfer Command" using an RRCConnectionReconfiguration message, which can now include fields that are "Optional continue", so the UE keeps its current settings to these parties if the corresponding fields are missing. It is thus possible to create a flexible protocol that allows reconfigurations, but where small message sizes can be provided in case only specific parts of configurable parts are reconfigured. Specifically, the solution is also applied to transfer.
    [0014] 3GPP protocols are published in different versions. Functionality can be changed between protocol versions and it is typical that enhanced, new functionality is added in new protocol versions. For example, after this, Rel-8 of the E-UTRAN protocols is considered to be functionally stable, future changes will be added to Rel-9, Rel-10, and so on.
    [0015] Typically, it is not possible to add non-reverse compatible functionality and protocol extensions to a stable protocol, as this can result in malfunctioning UEs and nodes already in the field that do not support such amendments. RCC is implemented using Abstract Syntax Notation One (ASN.1) by which messages can be extended in new versions. Such extensions typically include relevancy parameters for functionality that is added in a later release. Both “non-critical” and “critical” extensions can be added.
    [0016] A critical extension implies that a recipient of an earlier version of such an extension will not understand the content of the message. For example, if a Rel-9 eNB sends a Rel-9 message to a Rel-8 UE, where the message includes a critical extension, then the UE may fail to decode the message.
    [0017] A non-critical extension has the characteristics that a receiver of an earlier version can ignore the non-critical extension, but the receiver can still successfully decode the parts of the message that comply with the earlier version. For example, if a Rel-9 eNB is going to send a message to a Rel-8 UE, where the message includes a non-critical extension, then the UE can still decode parts of the message that follow the Rel-8 syntax. RCC Rel-8 includes placeholders in messages and IEs relevant to such non-critical extensions. This has been done in order to prepare for the extendibility of the RRC protocol.
    [0018] It has been noted that “optional continue” may cause a transfer issue for those cases where Source eNB and Target eNB implement different protocol version versions. Suppose the Target eNB implements a protocol and is functionally specified in Rel-8. Also assume that the eNB Fonte implements a later version with additional functionality, eg Rel-9. It is further assumed that the functionality added in the RRC Rel-9 protocol is added using protocol extensions and that the UE is configured with these features associated with the new Rel-9 features. A problem related to this scenario occurs if the above mentioned new information elements or fields in a later version (eg Rel-9) are added using critical extensions, eg the source eNB sends a HandoverPreparationInformation Rel-9 message to the Target eNB, since the exemplified Rel-8 Target eNB may fail to decode the Access Layer Context message received in the handover preparation message. In such a case, the Target eNB may have to send a complete reconfiguration message to the UE in the "transfer command", as the Target is unable to decode the UE configuration, eg Target eNB does not know what configuration the UE currently has. have. Thus, “Optional continue” may be impossible for previous version eNB, and large transfer messages will be needed. Another related problem occurs if the aforementioned new information elements or fields in a later version (eg Rel-9) are added using non-critical extensions. In this case, the exemplified Target Rel-8 eNB supporting an earlier version can successfully decode the parameters included in the earlier version. However, the Target eNB will not understand the encoding of the fields released later, and will have to ignore these fields. Thus, these fields will not be present in the “transfer command”, since the Target eNB will not know how to encode such fields.
    [0019] The problem occurs on the later version UE (eg Rel-9) that receives the “transfer command”. If the “Optional continue” principle was to be implemented for new fields, then the UE should continue using the configured later version features after transfer without any changes. However, in the example, the absence of these new fields was due to the fact that the eNB Target did not understand these fields, and the eNB Target clearly does not support later version protocol features. Thus, a mismatch can occur, where the UE continues to use functionality that the Target eNB does not implement, and severe protocol and functional errors can occur, since hierarchical communication entities (UE and Target eNB) will assume different configurations. summary
    [0020] Consequently, none of the prior art solutions described above offer the possibility to support “Optional continue” features for new functionality added in a later version, or the possibility for an earlier version of eNB Target to implement “Optional continue” when the eNB receives a configuration including fields from a later version that the eNB Target does not understand in part or completely. As stated above, “Optional continue” implies that the UE must maintain configuration and related functionality associated with later version without changing any parameters at times when an optional field related to functionality is missing.
    [0021] It is thus the purpose of the present invention to solve the aforementioned problems, and in particular, to provide a solution where the "Optional continue" feature can be implemented for protocol extensions added in future versions of a signaling protocol, such that the user equipment can implement both “optional continue” and “discontinue, release” in the absence of the aforementioned protocol extensions in an eNB that the UE is connected to or is to be connected to.
    [0022] According to a first aspect, a method at a base station is provided. The base station is suitable for configuring a UE in a handover scenario, when the UE is handover from a source base station to the base station and where the base station does not support at least one functionality whose source base station is the UE support. In the method, an HO request message is received from the source base station comprising at least a first field associated with a first feature not supported by the base station. At least a portion of the HO request message is decoded. Additionally, a reconfiguration message to be used to configure the UE to be transmitted to the base station is composed. Composition comprises omitting insertion of at least a first field, and inserting a second field. The second field being indicative of how the UE is to be configured with respect to the first functionality, and the composite reconfiguration message is sent to the UE via the source base station.
    [0023] According to a second aspect of the present invention a method in a UE is provided. The UE is configured to be handed over from a source base station to a target base station in a handover scenario, where the target base station may not support features which the source base station and UE support. In the method, a configuration message is received from the target base station via the source base station, and the UE is configured based on the configuration message received from the target base station. Configuration is achieved by looking for a second field in an information element of the received configuration message. The presence/non-presence or a value of the Second field is indicative of how to manage a first configured functionality associated with an optional first field, where the first configured functionality may not be supported by the target base station.
    [0024] According to a third aspect of the present invention, a base station to configure a UE in a handover scenario is provided. In the handover scenario, the UE is handover from a source base station to the base station, wherein the base station is configured not to support at least one functionality which the source base station and the UE support. The base station comprises a receiver configured to receive from the source base station an HO request message comprising at least a first field associated with a first functionality not supported by the base station and a decoder configured to decode at least a portion of the request message of HO received. The base station further comprises a processor configured to compose a reconfiguration message to be used to configure the UE to be transferred to the base station. The processor is further configured to omit insertion of at least a first field, and to insert a second field where the second field is indicative of how the UE is to be configured with respect to the first functionality. The base station further comprises a transmitter for sending the composite reconfiguration message to the UE via the source base station.
    [0025] According to a fourth aspect of the present invention, the UE configured to be handed over from a source base station to a target base station in a handover scenario is provided. The target base station may not support functions that the source base station and UE support. The UE comprises a receiver configured to receive a configuration message from a target base station via the source base station. Additionally, the UE comprises a processor configured to search for a second field in an information element of the received configuration message. The presence/non-presence or a value of the second field is indicative of how to manage a first configured functionality associated with an optional first field, where the first configured functionality may not be supported by the target base station.
    [0026] An advantage of the embodiments of the present invention is that they make it possible to implement "Optional continue" for configurations associated with optional fields, when optional fields are absent, wherein the optional fields are related to said configurations so that small messages can be supported.
    [0027] At the same time, it is possible to implement yet another case, e.g. that the receiver disables the associated features in times of the non-presence of optional fields, in which the non-presence can be caused by the fact that the transmitter supports a later version of the protocol, where optional fields and related functionality are not yet supported.
    [0028] Thus, embodiments of the present invention allow small reconfiguration messages in future protocol versions and support compatibility between nodes in a heterogeneous network with nodes supporting different versions.
    [0029] Other objects, advantages and new features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
    [0030] Figure 1 illustrates a message comprising information elements and according to the prior art.
    [0031] Figure 2 illustrates a mobility scenario according to the prior art.
    [0032] Figure 3 illustrates a mobility scenario.
    [0033] Figures 4 and 5 illustrate flowcharts of methods according to embodiments of the present invention.
    [0034] Figure 6 illustrates arrangements for carrying out the methods as described in the embodiments of the present invention. Detailed Description
    [0035] The present invention will be described more fully herein with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. The invention may, however, be an embodiment in different forms and should not be construed as limited to the embodiments shown here; moreover, these embodiments are provided so that this disclosure will be thorough and complete, and will completely transfer the scope of the invention to those skilled in the art. In the drawings, as reference signs refer to elements of the type.
    [0036] Additionally, those skilled in the art will appreciate that the means and functions discussed here below can be implemented using software working in conjunction with a general purpose programmed microprocessor or computer, and/or using an application-specific integrated circuit (ASIC). It will also be appreciated that while the present invention is primarily described in the form of methods and devices, the invention may also be in embodiment in a computer program product as well as a system comprising a computer processor and a memory coupled to the processor, wherein the memory is encoded with one or more programs that can perform the functions disclosed here.
    [0037] It should be noted that the embodiments of the present invention will be described in the context of an LTE network, but it should be noted that the invention is applicable in any system having base stations of different versions.
    [0038] The following detailed description describes embodiments of the present invention illustrated by means of specific examples. In the examples it is assumed that a handover of a User Equipment (UE_ must be performed from a first base station to a second base station also referred to a source base station and a target base station, respectively. It should also be noted that the base stations are referred to as eNBs as the modalities below are described in conjunction with LTE. The first eNB comprises at least one functionality supporting a certain UE configuration which is not comprised in the second eNB. In the description below this is described how the first eNB is version later than the second eNB. The later version is exemplified as LTE Rel-9 and the version of the second eNB is exemplified as LTE Rel-8. Additionally, the UE is configured with new functionality that is not supported in LTE Rel-8. new functionality is associated with the first field of an Information Element (IE) of a message according to the Rel-9 signaling protocol. characterized by multiple such first fields of an Information Element of a message. It should be understood that the example is equally valid for any scenario where the source eNB and the UE support functionality not yet supported by the target eNB.
    [0039] Examples of new features are channel quality indication (CQI) reporting features, timer handling, carrier aggregation, enhanced DRX, retransfer, coordinated multi-point transfer and reception, and any other features that may be included in a future version of the protocol.
    [0040] According to embodiments of the present invention with reference to Figure 3, the source eNB 310 sends 301 a message 330 to the target eNB 312, where the message 330 comprises an information element (IE) 320 which in turn comprises a first field 322 relating to a UE configuration supported by the source eNB 310 but not supported by the target eNB 312. The IE 320 further comprises other UE configurations supported by both the source and the Target eNB. In this example, the first field is encoded as non-critical version 9 extensions. The UE configuration is typically tunneled or modalized into a "Transfer Request" message from the source eNB 310 to the target eNB 312. The target eNB 312 is capable of decoding the message, except for non-critical extensions, that the target eNB 312 ignores. Since the target eNB 312 does not support the UE configuration associated with the first field, the Target eNB 312 omits the first field when creating 302 the reconfiguration message to be sent to the UE 314 via the source eNB 310. Instead, the eNB target can add a signaling or other indication in a second field where it is indicated that the target eNB does not support the UE configuration that is supported by the UEs and eNBs of later versions by e.g. telling the UE to stop using the UE configuration .
    [0041] According to further embodiments the target eNB indicates to the UE in the second field the current version that is supported by the target base station and/or the RRC functionalities that the target base station supports.
    [0042] Subsequently, the target eNB 312 now sends 303 a transfer command using, e.g., an RRCConnectionReconfiguration message, where this message is encoded according to the version supported by the target eNB 312. This RRC Connection reconfiguration message is addressed to the UE, and is typically tunneled or modalized in a Transfer Acknowledgment message from the target eNB to the source eNB. The Reset message is typically passed unmodified, eg transparently, via the source eNB. Thus, it is the target eNB that takes responsibility for configuring the UE in a way that is suitable for the target eNB once the handover is completed.
    [0043] Thus, the message received in the UE does not include the first field related to the configuration not supported by the target eNB. According to the present invention the UE detects 304 the signaling of the second field and then the UE understands that the UE should release which setting, if the first field is omitted. Since the UE supports the later version of the protocol compared to the target eNB, the UE will know from the standard description how to behave with the above mentioned later version feature when the signaling of the second field is included in the Handover message.
    [0044] From a UE perspective, the UE does not know which version the target eNB supports. According to an embodiment of the present invention, the UE can distinguish between the following two cases if the first field can be omitted in a reconfiguration message: (1) The target eNB asks the UE to continue with the UE configuration associated with the omitted field; (2) The target eNB does not support the UE configuration associated with the skipped field, and instructions according to the UE must stop using the UE configuration.
    [0045] In said method according to the embodiments of the present invention, the UE receives the configuration message e.g. in the transfer command that does not include the first field related to the new functionality. The first field is thus coded as optional. However, in order to deduce what actions the UE should take now, when the first field is not present, the UE checks the presence or a value of a second field. This second field is typically also coded as optional.
    [0046] If said second field is present or has a specific value, the UE takes a first action regarding the functionality associated with the fields related to the new functionality. If said second field is not present or has another specific value, the UE takes a second action regarding the new functionality associated with the fields. As an example of a first action in case the second movie is present, which indicates that the target eNB does not support the associated UE configurations, the UE can be configured to discontinue with the associated UE configuration. This may imply that a fullConfig parameter is entered in the second field. As an example of a second action in case the second field is not present, which indicates that the target eNB supports the associated functionality, the UE is configured to continue using the functionality associated with the first field.
    [0047] The second field above may be included in the same IE or in a different IE as the first field associated with functionality that the target base station may not support. An example of an IE where the second field can be added is the MobilityControl IE in the RRC protocol. The above-mentioned search performed by the UE of the presence or value of the second field under detection that the first field is missing can be performed on handover, e.g. that the UE decides between taking the first or second action only if the message is a message that triggers a transfer. Thus, the MobilityControl IE is a conceivable example of where the second field might be included, and it should be understood that in other embodiments any IR in the HO command that is not directly associated with the new functionality in question could be used. As explained above, the indication in the second field could be an indication to the UE to continue with previously configured functionality within a certain set of new functionality, if the corresponding configuration information is absent in the HO command, e.g. when the first field is omitted. Such a set of new functionality can be defined as new functionality introduced within a specific version of the specification or a more specifically defined group of functionality. For example, if a UE is configured according to an N+4 version, but the target eNB only supports N+2 version, the new functionality introduced in each version can be grouped, so that the UE, depending on the value or presence from the second field, you are instructed to continue with parts of the new feature, and discontinue with parts of other new features introduced after N+2 version, but to continue with all new features introduced before N+2. Thus, new functionality that is subject to the above mentioned evaluation in UE can be bundled in each version. This indication could be done with a second field separated by version, or with a second table that can take multiple values.
    [0048] To summarize a method at a base station according to embodiments of the present invention is provided. The base station is configured to act as a target base station in a handover scenario when a UE is handover from a source base station to the target base station and where the target base station does not support at least one function in which the station base source and UE support.
    [0049] As illustrated in Figure 4, an HO request message is received 401 from the source base station comprising at least a first field of an information element associated with a first functionality, e.g. an RRC functionality, not supported by the station target base. The target base station 402 decodes at least a portion of the received HO request message, and composes 403 a reconfiguration message to be used to configure the UE to be transferred to the target base station. Composition 403 comprises omitting 404 insertion of at least a first field, and inserting 405 a second field. The second field indicates how the UE should be configured in relation to the first functionality. The base station then sends 406 the composite reconfiguration message to the UE via the source base station.
    [0050] According to an embodiment of the present invention, the indication in the second field how the UE should be configured in relation to the first functionality indicates to the UE to discontinue the use of the first functionality not being supported by the target base station. Another possibility is that the indication in the second field indicates to the UE the current version that is supported by the target base station and/or the features that the target base station supports.
    [0051] Additionally, a method in a UE is provided as illustrated in figure 5. The UE is configured to be handed over from a source base station to the target base station in a handover scenario where the target base station may not support features, eg EEC features, which the source base station and UE support. The UE receives 501 a configuration message from a target base station via the source base station and 502 configures the US based on the configuration message received from the target base station. Configuration is performed by looking 503 for a second field in an information element of the received configuration message. The presence/non-presence or a value of the second field is indicative of how to manage a first configured functionality associated with an optional first field, where the first configured functionality may not be supported by the target base station.
    [0052] The value of the second field can be the presence or non-presence of a signal, where the signal can be a fullConfig signal.
    [0053] According to embodiments of the present invention, the presence of the second field or signaling indicates to the UE to discontinue the use of the first functionality and the absence of the second field or signaling indicates to the UE to continue using the first functionality. Additionally, the value of the Second field may indicate to the UE the current version that is supported by the target base station and/or the features that the target base station supports.
    [0054] Turning now to Fig. 6 illustrating a base station 600 for configuring a UE 620 in a handover scenario, when the UE 620 is handover from a source base station to base station 600. Base station 600 is configured not to support at least one functionality that the source base station and UE 620 support. Base station 600 comprises a receiver/transmitter and other RF functionality to communicate with UEs and the base station is also configured to communicate with other base stations. Furthermore, processing units required for functionalities not relevant to the invention are omitted from the drawings and specification.
    [0055] The base station 600 comprises a receiver 601 configured to receive a transfer request (HO) message from the source base station comprising at least one field of an information element associated with a first functionality not supported by the base station. Base station 600 further comprises a decoder 602 configured to decode at least a portion of the received HO request message, depending on whether the HO request message is decoded with critical or non-critical extensions for a version of a protocol that the target base station does not. supports. The base station further comprises a processor 603 configured to compose a reset message to be used to configure the UE to be transferred to the target base station. Also, processor 603 is further configured to omit insertion of at least a first field, and to insert a second field, wherein the second field is indicative of how the UE is to be configured with respect to the first feature. Additionally the base station comprises a transmitter 604 configured to send the composite reconfiguration message to the UE via the source base station.
    [0056] Thus the base station according to embodiments of the present invention can be a base station having the functionalities of an LTE 8 version with the addition of the mechanisms provided by the embodiments of the invention as defined above.
    [0057] As illustrated in Fig. 6, the UE 620 comprises a receiver/transmitter 621 and other RF functionality to communicate with the network. Furthermore, processing units required for functionalities not relevant to the invention are omitted from the drawings and specification. In accordance with the present invention UE 620 comprises a receiver configured to receive a configuration message from the target base station via the source base station. A processor 622 is not configured to look for a background in an information element of the received configuration message. The presence/non-presence or a value of the second field is indicative of how to manage a first configured functionality associated with an optional first field, where the first configured functionality associated with an optional first field, where the first configured functionality may not be supported by the target base station.
    [0058] According to an embodiment of the present invention, the processor is configured to interpret the presence of the second field or the signaling as to discontinue the use of the first functionality. Additionally, the processor can be configured to interpret the non-presence of the second field or the signaling as to continue using the first functionality.
    [0059] It should be noted that the processor can be configured to interpret the value of the second field as the current version that is supported by the target base station and/or the RCC functionalities that the target base station supports.
    [0060] According to a further alternative to solve the problem associated with networks comprising base station of different versions, the Source eNB may send a handover preparation message to the Target eNB, so that the message includes at least two alternative representations of the UE Access Layer Configuration. The messages are encoded so that the Target eNB can decode at least one of the representations of the Access Layer Configuration, irrespective of the version of the Target eNB. Specifically, one of the encoded representations of the Access Layer Configuration may be encoded in accordance with a first version of the protocol, and another encoded representation of the Access Layer Configuration may be encoded in accordance with another version of the protocol. The other version of the protocol can now include critical extensions in the message or IE representing the Access Stratum Configuration.
    [0061] This mechanism of including multiple representations ensures that the Target eNB always receives a representation that it can decode, regardless of the version the Target eNB supports, and critical protocol extensions can now be included in IEs describing the AS Context in future versions of the protocol. The Target eNB then selects one of the Access Layer Configuration encoded representations, on the basis of which it encodes a transmit command that it sends in an RRCConnectionReconfiguration message.
    [0062] The UE can then, based on the encoding of the RRCConnectionReconfiguration message or IEs in the target eNB message, sent through the source eNB, deduce whether to apply the first action or the second action in relation to the new functionality. Specifically, if the message includes a specific critical extension associated with the new functionality, the UE may apply a first action, and if the message does not include a specific critical extension associated with the new functionality, the UE may apply a second action. The first action above might be to continue using new functionality, and the second action might be to stop using new functionality. Thus, by detecting the above-mentioned message encoding method, the UE can deduce whether the handover entity, e.g. the Target eNB, supports specific functionality and what actions should be taken based on this.
    [0063] As explained above, it is proposed to send (at least) two representations of the current UE configuration to the target eNB, one based on a "backward" version of the protocol, and a critically extended version supporting the full UE configuration . In this specification, LTE Rel-8 is exemplified as the “backward” version.
    [0064] However in the future, if for example LTE Rel-9 and LTE Rel-10 are readily implemented in both the source and the target eNB, it might be desirable not to have to send a large range of "backward" alternatives just because the precise state of the hierarchy is not known. thus in an additional mode it is “negotiated” between the source and target eNB when establishing the X2 link to determine which protocol version to use. this can be done, eg if each node indicates to the other up to which protocol version it supports. The two entities thus provide at least one commonly supported version as the “backward” version. A first eNB may request release version information supported by a second eNB. Based on knowledge of the released version of the Target eNB, a source eNB can now decide to submit an Access Layer Configuration that the Target understands. Still, also with the different modalities related to the solution of sending information between the eNBs regarding the current UE configuration encoded according to different protocol versions, there is need for an indication by which the UE decides how to act when optional fields or IEs of an later version protocol are not present in a message.
    [0065] Modifications and other embodiments of the disclosed invention will come to mind to one skilled in the art having the benefit of the teachings presented in the descriptions that follow and the associated drawings. Thus, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be used here, they are used in a general and descriptive sense only and not for limiting purposes.
    权利要求:
    Claims (26)
    [0001]
    1. Method, at a base station, for configuring a user equipment, UE, in a handover scenario, when the UE is handover from a source base station to the base station and the base station implements a specified protocol and functionality in a first version and in which the source base station and the UE implement a later version with additional functionality, the method is characterized in that it comprises: - receiving (401) from the source base station a handover request message, HO, comprising at least a first field associated with a first feature, where the first feature is an additional feature implemented in the later version; - decoding (402) at least a portion of the received HO request message, - composing (403) a reconfiguration message to be used to configure the UE to be transmitted to the base station, wherein composing (403) comprises: - omitting (404) the insertion of the at least the first field, and inserting (405) a second field, the second field being indicative of how the UE is to be configured with respect to the first functionality, and - sending (406) the reconfiguration message to the UE via the source base station.
    [0002]
    2. Method according to claim 1, characterized in that the first functionality not supported by the base station is at least one of channel quality indication, CQI, reporting features, timing handling, carrier aggregation, discontinuous reception enhanced, transfer, and coordinated multipoint reception and transmission.
    [0003]
    3. Method according to claim 1 or 2, characterized in that the indication in the second field, how the UE must be configured in relation to the first functionality, indicates to the UE to discontinue the use of the first functionality not being supported by the station base.
    [0004]
    4. Method according to claim 1 or 2, characterized in that the indication in the second field, how the UE must be configured in relation to the first functionality, indicates to the UE the current version that is supported by the base station.
    [0005]
    5. Method according to claim 1 or 2, characterized in that the indication in the second field, how the UE must be configured in relation to the first functionality, indicates to the UE the functionalities that the base station supports.
    [0006]
    6. Method according to any one of claims 1 to 5, characterized in that the indication in the second field is the presence or non-presence of a flag.
    [0007]
    7. Method according to claim 6, characterized in that the flag is a fullConfig flag.
    [0008]
    8. Method, in a user equipment, UE, configured to be transferred from a source base station to a target base station in a handover scenario, and wherein the target base station implements a protocol and functionality specified in a first version and wherein the source base station and the UE implement a later version with additional functionality, the method characterized in that it comprises: - receiving (501) a target base station setup message via the source base station, - configuring (502) the UE based on the configuration message received from the target base station: - detecting (304, 503) a second field in an information element of the received configuration message, wherein the presence/non-presence of the second field is indicative of how manage a first configured functionality associated with an optional first field, where the first configured functionality is additional functionality implemented in the later version.
    [0009]
    9. Method according to claim 8, characterized in that the value of the second field is the presence or non-presence of a flag.
    [0010]
    10. Method according to claim 9, characterized in that the flag is a fullConfig flag.
    [0011]
    11. Method according to any one of claims 8 to 10, characterized in that the first functionality is at least one of channel quality indication, CQI, reporting features, timer handling, carrier aggregation, enhanced discontinuous reception , transfer, and coordinated multipoint reception and transmission.
    [0012]
    12. Method according to any one of claims 8 to 11, characterized in that the presence of the second field or the flag indicates to the UE to discontinue the use of the first functionality.
    [0013]
    13. Method according to any one of claims 8 to 11, characterized in that the non-presence of the second field or flag indicates to the UE to continue using the first functionality.
    [0014]
    14. Method according to any one of claims 8 to 11, characterized in that the value of the second field indicates to the UE the current version that is supported by the target base station.
    [0015]
    15. Method according to any one of claims 8 to 11, characterized in that the value of the second field indicates to the UE the RRC functionalities that the target base station supports.
    [0016]
    16. Base station (600) to configure a user equipment, UE (620), in a handover scenario, when the UE (620) is handover from a source base station to the base station (600) and where the station base (600) implements a protocol and functionality specified in a first version and where the source base station and the UE implement a later version with additional functionality, the base station (600) characterized by the fact that it comprises: a receiver (601) configured to receive from the source base station a handover request message, HO, comprising at least a first field associated with a first functionality, the first functionality being an additional functionality implemented in the later version, a decoder (602) configured to decode at least a portion of the received HO request message, a processor (603) configured to compose a reconfiguration message to be used to configure the UE to be transferred gone to the base station, wherein the processor (603) is further configured to omit insertion of the at least first field, and to insert a second field, the second field being indicative of how the UE is to be configured with respect to the first functionality , and a transmitter (604) for sending the composite reconfiguration message to the UE (620) via the source base station.
    [0017]
    17. Base station according to claim 16, characterized in that the indication in the second field, how the UE must be configured in relation to the first functionality, is adapted to indicate to the UE to discontinue the use of the first functionality not being supported by the base station.
    [0018]
    18. Base station according to claim 16, characterized in that the indication in the second field, how the UE is to be configured in relation to the first functionality, is adapted to indicate to the UE the current version that is supported by the base station.
    [0019]
    19. Base station according to claim 16, characterized in that the indication in the second field, how the UE is to be configured in relation to the first functionality, is adapted to indicate to the UE functionalities that the base station supports.
    [0020]
    20. User equipment, UE (620), configured to be handed over from a source base station to a target base station (600) in a handover scenario, and wherein the target base station implements a protocol and functionality specified in a first version and in which the source base station and the UE implement a later version with additional functionality, the user equipment UE (620) is characterized in that it comprises: a receiver (621) configured to receive a configuration message from the target base station via the source base station, a processor (622) configured to detect a second field in an information element of the received configuration message, wherein the presence/non-presence or a value of the second field is indicative of how to manage a first functionality configured associated with an optional first field, where the first configured functionality is additional functionality implemented in the later version.
    [0021]
    21. User equipment, UE (620) according to claim 20, characterized in that the value of the second field is a flag.
    [0022]
    22. User equipment, UE (621) according to claim 21, characterized in that the flag is a fullConfig flag.
    [0023]
    23. User equipment, UE (621) according to any one of claims 20 to 22, characterized in that the processor (622) is configured to interpret the presence of the second field or the flag as to discontinue use of the first functionality.
    [0024]
    24. User equipment, UE (621) according to any one of claims 20 to 23, characterized in that the processor (622) is configured to interpret the non-presence of the second field or flag as to continue using the first feature.
    [0025]
    25. User equipment, UE (621) according to any one of claims 20 to 23, characterized in that the processor (622) is configured to interpret the value of the second field as a current version which is supported by the base station target.
    [0026]
    26. User equipment UE (621) according to any one of claims 20 to 23, characterized in that the processor (622) is configured to interpret the value of the second field as the functionalities that the target base station supports.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012007188B1|2021-06-08|method on a base station to configure user equipment in a transfer scenario, method on a user equipment configured to be transferred from a source base station to a target base station in a transfer scenario, base station to configure a transfer equipment user in a handover scenario, user equipment configured to be transferred from a source base station to a target base station in a handover scenario
    US11044628B2|2021-06-22|Method and apparatus for processing state information in communication system
    BRPI0907368B1|2020-09-29|SIGNALING METHOD BETWEEN A MOBILE DEVICE AND A NETWORK NODE
    BR112012020138B1|2021-02-02|method for processing the mbms service session of the multimedia broadcast / multicast service on a ran radio access network
    ES2365979T3|2011-10-14|METHOD AND SYSTEM FOR EXCHANGING NETWORK MANAGEMENT CONFIGURATION INFORMATION BETWEEN NETWORK ELEMENTS MANAGEMENT SYSTEMS.
    BR112019010621A2|2019-09-17|communication method and communication apparatus
    BR112021002044A2|2021-05-04|measurement and apparatus setup method
    WO2020090987A1|2020-05-07|Methods and apparatus for using redundant links in wireless backhaul
    BR112020018453A2|2020-12-29|METHOD AND APPARATUS FOR UPDATING A USER EQUIPMENT POLICY
    BR112020005105A2|2020-09-15|data processing method and terminal device
    US20100271979A1|2010-10-28|Methods To Facilitate Automatic System Configuration
    BR112020020799A2|2021-01-12|DATABASE SYNCHRONIZATION POINT TO POINT ABOUT A TRANSPORT PROTOCOL
    BR112021005816A2|2021-06-29|cell reselection method and communications apparatus
    KR20180008911A|2018-01-24|Information interaction device, base station and communication system
    BR112021011583A2|2021-08-31|SIDE LINK COMMUNICATION METHOD AND TERMINAL DEVICE
    BR112020014798A2|2020-12-08|DATA TRANSMISSION METHOD, TERMINAL DEVICE AND COMPUTER STORAGE MEDIA
    BR112019026135A2|2020-06-30|paging fault processing method, access network device and main network device
    BRPI1012995B1|2021-07-06|METHOD, MOBILE STATION AND BASE STATION TO PROVIDE AN INDICATOR OF THE PRESENCE OF A FIRST ACCESS NETWORK THAT IS CAPABLE OF INTEROPERATING WITH A SECOND ACCESS NETWORK
    BR112020009788A2|2020-10-13|apparatus and method of signal transmission
    WO2020153274A1|2020-07-30|Cell selection on a radio link failure in wireless relay networks
    WO2010121496A1|2010-10-28|Method and device for processing a measurement context
    WO2021155863A1|2021-08-12|Method and apparatus for processing integrated access backhaul wireless link recovery failure, and communication device
    BR112021001197A2|2021-04-27|terminal apparatus, base station apparatus and method
    BR112020021118A2|2021-03-23|methods of operating a wireless terminal, operating a base station on a radio access network, and operating a wireless terminal or user equipment, wireless device, and base stations on a wireless communication network wireless network and a radio access network
    BR112021013953A2|2021-09-21|COMMUNICATION METHOD AND COMMUNICATION DEVICE
    同族专利:
    公开号 | 公开日
    CN102550080A|2012-07-04|
    PL2484148T3|2014-07-31|
    US20120178456A1|2012-07-12|
    ES2458548T3|2014-05-06|
    US9924420B2|2018-03-20|
    EP2484148A1|2012-08-08|
    US20170105151A1|2017-04-13|
    US9532279B2|2016-12-27|
    RU2540961C2|2015-02-10|
    US20180184342A1|2018-06-28|
    US20150148044A1|2015-05-28|
    RU2012117732A|2013-11-10|
    HK1172479A1|2013-04-19|
    BR112012007188A2|2016-03-29|
    US10264497B2|2019-04-16|
    EP2484148B1|2014-03-05|
    WO2011040857A1|2011-04-07|
    CN102550080B|2016-03-16|
    US8971891B2|2015-03-03|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    KR100424472B1|2001-09-11|2004-03-26|삼성전자주식회사|Method for processing idle handoff between base stations supporting different services|
    US8526950B2|2003-12-30|2013-09-03|Nokia Corporation|Determining handover based on state of mobile terminal|
    US20080161000A1|2006-12-28|2008-07-03|Nokia Corporation|Apparatus, method and computer program product providing faster handover in mobile wimax system|
    AU2008214411B2|2007-02-02|2012-02-02|Interdigital Technology Corporation|Method and apparatus for controlling a handover between UTRA R6 cells and R7 cells|
    US8125954B2|2007-05-04|2012-02-28|Futurewei Technologies, Inc.|System for FA relocation with context transfer in wireless networks|
    US9392504B2|2007-06-19|2016-07-12|Qualcomm Incorporated|Delivery of handover command|
    WO2010002229A2|2008-07-04|2010-01-07|Lg Electronics Inc.|Method for transmitting information for inter-radio access technology handover|
    KR101555061B1|2008-08-22|2015-09-23|엘지전자 주식회사|Method of performing cell re-search between heterogeneous networks|
    CN101394359B|2008-10-31|2011-07-27|北京邮电大学|Communication system and method for supporting end-to-end QoS in heterogeneous wireless network|
    CN102550080B|2009-09-30|2016-03-16|瑞典爱立信有限公司|Method and apparatus in mobile communication system|CN102550080B|2009-09-30|2016-03-16|瑞典爱立信有限公司|Method and apparatus in mobile communication system|
    GB2474077B|2009-10-05|2013-07-24|Samsung Electronics Co Ltd|Method and apparatus for configuring radio access functionality of a wireless commumication unit|
    EP2941084B2|2009-12-15|2020-04-08|Wireless Future Technologies Inc.|Methods, apparatuses and related computer-readable storage medium for deciding on a signaling scheme for handover|
    EP2728933A4|2011-06-28|2015-05-20|Kyocera Corp|Communication control method and home base station|
    US8395985B2|2011-07-25|2013-03-12|Ofinno Technologies, Llc|Time alignment in multicarrier OFDM network|
    US9237537B2|2012-01-25|2016-01-12|Ofinno Technologies, Llc|Random access process in a multicarrier base station and wireless device|
    US8526389B2|2012-01-25|2013-09-03|Ofinno Technologies, Llc|Power scaling in multicarrier wireless device|
    US8995405B2|2012-01-25|2015-03-31|Ofinno Technologies, Llc|Pathloss reference configuration in a wireless device and base station|
    KR101885540B1|2012-03-23|2018-09-11|주식회사 골드피크이노베이션즈|Apparatus and method for uplink synchronizing in multiple component carrier system|
    EP2835023B1|2012-04-01|2021-09-01|Comcast Cable Communications, LLC|Cell group configuration in a wireless device and base stationwith timing advance groups|
    US20130259008A1|2012-04-01|2013-10-03|Esmael Hejazi Dinan|Random Access Response Process in a Wireless Communications|
    US8995381B2|2012-04-16|2015-03-31|Ofinno Technologies, Llc|Power control in a wireless device|
    US8964593B2|2012-04-16|2015-02-24|Ofinno Technologies, Llc|Wireless device transmission power|
    US11252679B2|2012-04-16|2022-02-15|Comcast Cable Communications, Llc|Signal transmission power adjustment in a wireless device|
    US9210664B2|2012-04-17|2015-12-08|Ofinno Technologies. LLC|Preamble transmission in a wireless device|
    US8964683B2|2012-04-20|2015-02-24|Ofinno Technologies, Llc|Sounding signal in a multicarrier wireless device|
    US9107206B2|2012-06-18|2015-08-11|Ofinne Technologies, LLC|Carrier grouping in multicarrier wireless networks|
    US8971298B2|2012-06-18|2015-03-03|Ofinno Technologies, Llc|Wireless device connection to an application server|
    US9210619B2|2012-06-20|2015-12-08|Ofinno Technologies, Llc|Signalling mechanisms for wireless device handover|
    US9084228B2|2012-06-20|2015-07-14|Ofinno Technologies, Llc|Automobile communication device|
    US9179457B2|2012-06-20|2015-11-03|Ofinno Technologies, Llc|Carrier configuration in wireless networks|
    US9113387B2|2012-06-20|2015-08-18|Ofinno Technologies, Llc|Handover signalling in wireless networks|
    JP6052404B2|2012-06-27|2016-12-27|富士通株式会社|Apparatus coexistence configuration information processing method, apparatus and system|
    US20140064135A1|2012-08-28|2014-03-06|Texas Instruments Incorporated|Reception of Downlink Data for Coordinated Multi-Point Transmission in the Event of Fall-Back|
    JP6259578B2|2013-03-25|2018-01-10|株式会社Ｎｔｔドコモ|Mobile communication method|
    KR101814248B1|2014-09-05|2018-01-04|주식회사 케이티|Methods for transmitting data using a WLAN carrier and Apparatuses thereof|
    CN107071913B|2014-09-18|2020-04-21|株式会社Kt|Method and apparatus for processing user plane data|
    CN106717060B|2014-10-02|2020-06-05|株式会社Kt|Method for processing data using WLAN carrier and apparatus thereof|
    HUE051422T2|2015-06-12|2021-03-01|Ericsson Telefon Ab L M|Mobility for beam-forming systems|
    US9814050B2|2015-11-30|2017-11-07|Qualcomm Incorporated|Systems and methods for performing network configurable access and data transfer procedures|
    US10136309B2|2016-01-14|2018-11-20|Qualcomm Incorporated|Spectrum access server support of resource assignments based on radio access network coexistence information|
    US20180049255A1|2016-08-10|2018-02-15|Htc Corporation|Device and Method of Handling a Signaling Radio Bearer for Narrowband Internet of Things Communication|
    CN108234006B|2016-12-22|2020-07-24|大唐移动通信设备有限公司|Method and base station for configuring UEreporting PMIand RIin TM8 |
    CN107567062B|2017-10-09|2020-11-03|京信通信系统（中国）有限公司|Information processing method and device in network element switching process and network element equipment|
    CN109831810B|2017-11-23|2020-10-13|大唐移动通信设备有限公司|Method and device for establishing wireless access bearer|
    CN109874155B|2017-12-01|2020-08-28|大唐移动通信设备有限公司|Cell switching method and base station|
    CN111586619A|2019-02-15|2020-08-25|华为技术有限公司|Communication method and device under multiple network systems|
    法律状态:
    2019-01-15| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-03-03| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-03-17| B15K| Others concerning applications: alteration of classification|Free format text: A CLASSIFICACAO ANTERIOR ERA: H04W 36/00 Ipc: H04W 8/24 (2009.01), H04W 36/00 (2009.01), H04W 88 |
    2021-03-30| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-06-08| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 03/06/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF |
    优先权:
    申请号 | 申请日 | 专利标题
    US24703409P| true| 2009-09-30|2009-09-30|
    US61/247,034|2009-09-30|
    PCT/SE2010/050611|WO2011040857A1|2009-09-30|2010-06-03|Methods and arrangements in a mobile telecommunication system|
    [返回顶部]